Using geographical location information and at least one distance requirement to determine a target storage to provision to backup data for a source device

ABSTRACT

Provided are a computer program product, system, and method for using geographical location information to provision one or more target storages for a source device. A determination is made of a geographical location of the source device and of geographical locations of the target storages. A determination is made of one of the target storages whose distance from the source device based on the geographical locations of the source device and the target storages satisfies at least one distance requirement. A configuration procedure is initiated to configure the source device and the determined target storage to have the source data backed-up from the source device to the target storage over the network.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for using geographical location information to provision one ormore target storages for a source device.

2. Description of the Related Art

In network computing environments, an administrator will typicallyprovision backup storage devices to backup data from the source devicesin the network. The administrator may select one or more backup ortarget storages to receive the source device data. Selection of a dataprotection solution for storage devices generally depends on arbitrarydecisions or heuristics for selecting a data protection target. Forexample, all application servers supporting an organization might bebacked up to the same centrally located data-protection server, eventhough the protected application servers are geographically dispersed.Such an approach may result in operational inefficiency and/orinadequate disaster protection, especially in complex environments withdispersed data assets.

Further, in many customer environments, the location of the client datais in close proximity to the location of the data protection server towhich the data is being sent. In such configurations, if a disaster wereto befall the location of the backup and source data, then all copies ofthe data may be lost. To guard against such occurrences, many customersmake off-site copies of data, or use replication technologies (such asIBM® Tivoli® Storage Manager Node Replication) to make a disasterrecovery copy. (IBM and Tivoli are registered trademarks ofInternational Business Machines Corporation throughout the world)

There is a need in the art for improved techniques for provisioningstorage resources to client data for data protection and backup.

SUMMARY

Provided are a computer program product, system, and method for usinggeographical location information to provision one or more targetstorages for a source device. A determination is made of a geographicallocation of the source device and of geographical locations of thetarget storages. A determination is made of one of the target storageswhose distance from the source device based on the geographicallocations of the source device and the target storages satisfies atleast one distance requirement. A configuration procedure is initiatedto configure the source device and the determined target storage to havethe source data backed-up from the source device to the target storageover the network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a backup storage environment.

FIGS. 2 and 5 illustrate embodiments of a source device.

FIG. 3 illustrates an embodiment of a target storage data store entry.

FIG. 4 illustrates an embodiment of operations to select a targetstorage to backup source data from a source device.

FIGS. 6a, 6b, and 6c illustrate an embodiment of operations to select aplurality of target storages to backup source data from a source device.

FIG. 7 illustrates an embodiment of operations to optimally select atarget storage location of a plurality of potential target storagelocations at which to provide a new target storage.

FIG. 8 illustrates a computing environment in which the components ofFIGS. 1, 2, and 5 may be implemented.

DETAILED DESCRIPTION

In order to optimize the data protection location of backup sites, thelocation of the data must be considered. However, a data protectionsolution may involve contradictory location-related considerations. Forexample, data protection and recovery operations are typically mostefficient when data sources (the data to be protected) are close todata-protection targets (the servers/storage on which backed-up data isprotected), thereby minimizing data transfer time and consumption ofnetwork resources. On the other hand, disaster recovery requirementsdictate that these sources and targets be as far apart as possible (orat least that there be some required geographic separation) to allow fordata recovery even if there is a disaster at one of the locations. Atechnique is needed for optimizing a data protection solution based onsuch opposing location considerations.

Described embodiments provide techniques for selecting target storagesfor a source device that considers the location of the target storagesand source devices and determines one of the target storages whosedistance from the source device based on the geographical locations ofthe source device and the target storages satisfies at least onedistance requirement. In certain implementations, multiple distancerequirements, such as disaster impact diameters and a primary distancelimit for a source device may be considered. Described embodimentsfurther allow for the automatic initiation of a configuration procedureto configure the source device and the determined target storage tobackup the source data from the source device to the target storage overthe network. In this way, described embodiments provide for automated,explicit consideration of geographic factors to ensure thatdata-protection solutions are operationally efficient and compliant withdisaster recovery requirements.

Another technical problem in the prior art is how to select thelocations of multiple target storages to backup and protect data for asource device when there are multiple distance requirements, such asdisaster impact diameters and a primary distance limit for the serverwith respect to a primary target storage to which daily backups andrecoveries may be performed.

Described embodiments provide techniques for selecting multiple targetstorages to use to backup data for a source device by determining adistance between the source device and each of the target storages inthe network and between each pair of target storages. A determination isthen made of qualifying k-tuples of the target storages. A k-tuplecomprises a group of k target storages. In one embodiment, the k-tuplemay comprise an ordered or unordered list of k target storages to whichthe source data is to be backed-up, such that k is an integer valuegreater than or equal to two and less than or equal to m. In otherembodiments, the k-tuples may comprise other groups of target storages.A qualifying k-tuple has one target storage that satisfies a distancerequirement with respect to the source device and a distance between anytwo target storages in the k-tuple satisfies the distance requirement.The qualifying k-tuple are then used to backup the data for the sourcedevice

FIG. 1 illustrates an embodiment of a network storage environment 100having one or more source devices 200 ₁, 200 ₂ . . . 200 _(n) and aplurality of target storages 104 ₁, 104 ₂ . . . 104 _(m) thatcommunicate over a network 106. Each source device 200 ₁, 200 ₂ . . .200 _(n) has source data 108 in a source storage 110 that may backed-upto one or more of the target storages 104 ₁, 104 ₂ . . . 104 _(m).

FIG. 2 illustrates an embodiment of the source device 200, such assource devices 200 ₁, 200 ₂ . . . 200 _(n), as having a backup agent 202executing in the source device 200 to select target storages 104 ₁, 104₂ . . . 104 _(m) to use to backup the source data 108 at the sourcedevice 200. The backup agent 202 accesses information in a targetstorage data store 300, having information on the target storages 104 ₁,104 ₂ . . . 104 _(m), that is used to select one or more of the targetstorages 104 ₁, 104 ₂ . . . 104 _(m).

In one embodiment, the backup agent 202 may comprise a programdownloaded from a web site, and the target storage data store 300 may beincluded in the download as a self-contained look-up table. In suchcase, the backup agent 202 may rely on the information in the providedtarget storage data store 300. Alternatively, the backup agent 202 mayupdate the target storage data store 300 by downloading a currentversion from a remote web site having current target storageinformation. In a further embodiment, the backup agent 202 may obtainthe target storage data store 300 from a remote server. In yet a furtherembodiment, the backup agent 202 may populate the target storage datastore 300 by communicating with the target storages 104 ₁, 104 ₂ . . .104 _(m) over the network 106.

In one embodiment, the target storage data store 300 may comprise alook-up table. The target storage data store 300 may also comprise acommon data store such as Lightweight Directory Access Protocol (LDAP)data store or an Active Directory service.

In the above described embodiments, the backup agent 202 is locatedwithin the source device 200 for which a target storage is to beselected. In an alternative embodiment, the backup agent 202 may belocated in a separate network device from the source device 200, such asin a remote server or gateway server that manages backup storageprovisioning for multiple of the source devices 200 ₁, 200 ₂ . . . 200_(n).

A source device 200 ₁, 200 ₂ . . . 200 _(n) may have storage allocatedto function as a target storage for other source devices and a targetstorage may have storage allocated for a source device as well asstorage allocations for one or more target storage instances. One servermay host multiple virtual target storages and virtual source devices.Further, the target storages 104 ₁, 104 ₂ . . . 104 _(m) may include acontroller to provide access and management services over the network106.

The source devices 200 ₁, 200 ₂ . . . 200 _(n) and target storages 104₁, 104 ₂ . . . 104 _(m) may comprise an enterprise storagecontroller/server suitable for managing access to attached storagedevices. Alternatively, the source devices 200 ₁, 200 ₂ . . . 200 _(n)may comprise client devices or may comprise different types of computingsystems, such as enterprise storage servers, workstations, mainframes,mobile computing devices, personal computers, tablets, smartphones,portable computing devices, telephony, wearable computers, wheredifferent source devices 200 ₁, 200 ₂ . . . 200 _(n) may comprise thesame or different types of computing devices.

The network 106 may comprise a Storage Area Network (SAN), Local AreaNetwork (LAN), Intranet, the Internet, Wide Area Network (WAN),peer-to-peer network, wireless network, arbitrated loop network, etc.The storages 104 ₁, 104 ₂ . . . 104 _(m) and 110 may each be implementedin one or more storage devices, or an array of storage devicesconfigured as Just a Bunch of Disks (JBOD), Direct Access Storage Device(DASD), Redundant Array of Independent Disks (RAID) array,virtualization device, tape storage, flash memory, etc. The storagedevices in which the storages 104 ₁, 104 ₂ . . . 104 _(m) and 110 areimplemented may comprise hard disk drives, solid state drives (SSD)comprised of solid state electronics, such as a EEPROM (ElectricallyErasable Programmable Read-Only Memory), flash memory, flash disk,Random Access Memory (RAM) drive, storage-class memory (SCM), etc.,magnetic storage disk, optical disk, tape, etc. In further embodiments,one or more of the storages 104 ₁, 104 ₂ . . . 104 _(m) and 110 maycomprise a storage environment, such as a software defined storage,virtual storage, cloud provisioned storage, etc.

FIG. 3 illustrates an embodiment of an instance of a data store entry300, in the data store 300 for each of the target storages 104 ₁, 104 ₂. . . 104 _(m) including a target storage ID 302 identifying the targetstorage; a geographical location 304 of the target storage 302; andstorage attributes 306 providing information on the target storage 302,such as a type of storage device, e.g., SSD, disk, tape, etc.; a qualityof service level; a network connection rate, storage capacity/rate, andother possible storage characteristics or attributes that are used toselect an appropriate target storage.

FIG. 4 illustrates an embodiment of operations performed by the backupagent 202 to provision a target storage 104 ₁, 104 ₂ . . . 104 _(m) fora source device 200, such as one of the source devices 200 ₁, 200 ₂ . .. 200 _(n). Upon receiving (at block 400) a request to provision backupresources, the backup agent 202 determines (at block 402) a geographicallocation of the source device 200. If the source device 200 is a mobiledevice, then its geographical location may change frequently. In oneembodiment, the backup agent 202 may determine the geographical locationof the source device 200 by issuing a command to an operating system ofthe source device 200 to obtain the geographical location if the sourcedevice 200 has a Global Positioning System (GPS) component to provide anexact location. In a further embodiment, the backup agent 202 may usenetwork routing data to estimate the geographical location of the sourcedevice 200, such as by sending pings to known locations, using internetspeed check tools to establish location using routing data, performingtriangulation with network hops from the device to known servers, etc.In a yet further embodiment, the backup agent 202 may interact with auser of the source device 200, such as by rendering a user interfacewindow on a display or through voice commands, to request a user of thesource device 200 to input the geographical location of the sourcedevice 200.

The backup agent 202 further determines (at block 404) the targetstorages 104 ₁, 104 ₂ . . . 104 _(m) indicated in the data store 300. Inone embodiment, the backup agent 202 may determine target storages 104₁, 104 ₂ . . . 104 _(m) that have storage attributes 306 in their datastore entries 300, that satisfy storage attributes in backup policysettings for the source device 200, such as a quality of service level,storage throughput, network throughput, storage capacity, storage type,etc. In a further embodiment, the backup agent 202 may not narrow theset of available target storages 104 ₁, 104 ₂ . . . 104 _(m) accordingto storage attributes, and instead just consider all target storages 104₁, 104 ₂ . . . 104 _(m) indicated in the data store 300.

The backup agent 202 determines (at block 406) the geographicallocations 304 of the determined target storages 104 ₁, 104 ₂ . . . 104_(m) from the target server data store 300. The backup agent 202 thendetermines (at block 408) the target storage 104 whose distance from thesource device 200 satisfies at least one distance requirement. In oneembodiment, there may be only one distance requirement which specifies aminimum distance that the target storage must be from the source device200, such as a disaster impact diameter (DID) indicating a minimumdistance to backup the data to protect from an area wide disaster. Theremay be just one disaster impact diameter used for all target storages104 ₁, 104 ₂ . . . 104 _(m) and the source device 200. Alternatively,the target storages 104 ₁, 104 ₂ . . . 104 _(m) and source device 200may have different disaster impact diameters. In such case, the backupagent 202 would use the maximum disaster impact diameter of the targetstorage 104 ₁, 104 ₂ . . . 104 _(m) being considered and the sourcedevice 200.

In another embodiment, the distance requirement may comprise a primarydistance limit to indicate a maximum distance for the target storage 104₁, 104 ₂ . . . 104 _(m) to be from the source device 200 to allow forsufficient throughput and transfer rates for everyday production backupsand recoveries for the source device 200. In one embodiment, the primarydistance limit may be a fixed distance. In a further embodiment, theprimary distance limit may be determined by determining a maximumdistance from the source device 200 that still provides for a minimumdata throughput rate between a target storage at the maximum distanceand the source device 200. This maximum PDL may be determineddynamically by the backup agent 202 whenever performing the operationsof FIG. 4 to select target storages 104 ₁, 104 ₂ . . . 104 _(m), or maybe a default value determined empirically and included as a defaultsetting in the backup agent 202.

In a further embodiment, the at least one distance requirement mayinclude both disaster impact diameter and a primary distance limit, suchthat the target storage 104 ₁, 104 ₂ . . . 104 _(m) is selected that hasa distance from the source device 200 that exceeds the disaster impactdiameter but is less than the primary distance limit. Target storages104 ₁, 104 ₂ . . . 104 _(m) that do not satisfy this requirement are notselected. If there are multiple target storages 104 ₁, 104 ₂ . . . 104_(m) that satisfy the one or more distance requirements, then the backupagent 202 may select the target storage closest to the source device200. Upon selecting one of the target storage 104 ₁, 104 ₂ . . . 104_(m), referred to as target storage 104, the backup agent 202 mayinitiate (at block 410) a configuration procedure to configure thesource device 200 and the determined target storage 104, to have thesource data 108 backed-up from the source device 200 to the targetstorages 104, over the network 106. In one embodiment, the backup agent202 may issue commands to configure both the source device 200 and theselected target storage 104 to have the source data 108 backed up to theselected target storage 104. The backup agent 202 can use ApplicationProgramming Interfaces (APIs) or other remote configuration tools, suchas Tivoli® Remote Execution and Access (RXA) toolkit, to configure theselected target storage 104 and the source device 200 for the backupoperations. (TIVOLI is a registered trademark of International BusinessMachines Corporation throughout the world). In an alternativeembodiment, the backup agent 202 may report the configurationinformation to a storage administrator who would then manually configurethe source device 200 and the selected target storage for the backupoperations.

If there are no target storages 104 ₁, 104 ₂ . . . 104 _(m) that satisfythe one or more distance requirements, then the backup agent 202 mayreport an error message to the administrator. Alternatively, the backupagent 202 may select a closest target storage 104 to provide backupservices for the source device 200 and generate a message noting thatselection was made without satisfying the distance requirements.

FIG. 5 illustrates an additional embodiment of the source device 500,such as may be used with the source devices 200 ₁, 200 ₂ . . . 200 _(n)having a backup agent 502 to select one or more target storages 104 ₁,104 ₂ . . . 104 _(m) on which to backup data, a target storage datastore 504, such as the target storage data store 300, and a sourcedevice and target storage table 506 having information on distancesbetween the source device 500 being configured and each of the targetstorages 104 ₁, 104 ₂ . . . 104 _(m) and distances from each targetstorage to each other target storage.

FIGS. 6a, 6b, and 6c illustrate an embodiment of operations performed bythe backup agent 502 to determine a set of k target storages of the mpossible target storages 104 ₁, 104 ₂ . . . 104 _(m), where one of the ktarget storages comprises a primary backup storage and the other of thek target storages comprise secondary backup storages. The variable “k”may comprise any positive integer less than or equal to m. Initially, kmay have to be greater than or equal to two, but later may bedecremented to one. The backup agent 502 may generate or receive arequest to configure k target storages. Upon initiating (at block 600)an operation to determine k target storages of the target storages 104₁, 104 ₂ . . . 104 _(m), the backup agent 502 determines (at block 602)a geographical location of the source device 500, e.g., by issuing acommand to the source device operating system, using network routinginformation, querying the user, etc. The backup agent 502 determines (atblock 604) a geographical distance between the source device 500 andeach of the target storages 104 ₁, 104 ₂ . . . 104 _(m) and between eachpair of target storages 104 ₁, 104 ₂ . . . 104 _(m). This informationmay be maintained in the source device and target storage table 506,which may be part of the installed backup agent 502, downloaded from aremote server, or determined by querying the target storages 104 ₁, 104₂ . . . 104 _(m) in the network 106.

The backup agent 502 then determines (at block 606) qualifying k-tuplesof the target storages 104 ₁, 104 ₂ . . . 104 _(m) that have one targetstorage satisfying a distance requirement (e.g., disaster impactdiameter) and a primary distance limit, such as described above, withrespect to the source device 500 and that a distance between any twotarget storages in the k-tuple satisfies the distance requirement (e.g.disaster impact diameter). The k-tuple comprises a grouping of kelements, or in the described embodiments, target storages that as awhole satisfy the distance requirements applied by the backup agent 502.In one embodiment, the primary distance limit provides a distance limitto ensure a high level of throughput between the source device 500 andone of the target storages in the k-tuple. In one embodiment, the samedistance requirement, e.g., disaster impact diameter, may be used forthe source device 500 and the target storages 104 ₁, 104 ₂ . . . 104_(m). In a further embodiment, the source device 500 and the targetstorages 104 ₁, 104 ₂ . . . 104 _(m) may have different distancerequirements, such that the distance requirements for each pair ofdevices, source device 500 and target storages 104 ₁, 104 ₂ . . . 104_(m), must both be satisfied by each of the devices being compared inorder to be a qualifying k-tuple.

In the above embodiment, a qualifying k-tuple has k target storages,with one target storage satisfying two requirements, e.g., disasterimpact diameter and primary distance limit, with respect to the sourcedevice 500, and each pair of the k target storages satisfying a distancerequirement for the k target storages, such as a disaster impactdiameter. In an alternative embodiment, a qualifying k-tuple may satisfya different set of requirements. For instance, a qualifying k-tuple mayhave target storages that satisfy the distance requirement, e.g.,disaster impact diameter, between each pair of target storages, but nothave to satisfy the requirements with respect to the source device 500.In alternative embodiments, different tests may be used for the targetstorages or the target storages and the source device to determine aqualifying k-tuple.

If (from the yes branch of block 608 and the yes branch of block 610)there is only one qualifying k-tuple, then that qualifying singlek-tuple is selected (at block 612). If (from the yes branch of block 608and the no branch of block 610) there are multiple qualifying k-tuples,then the backup agent 502 determines (at block 614) a score of each ofthe qualifying k-tuples based on a distance between each of the targetstorages in the k-tuple from the source device 500. A “better” score maycomprise a score indicating less total distance between the k targetstorages and the source device 500. In an alternative embodiment,different criteria may be used to score the k-tuples, such as distancebetween the k target storages, throughput, geographical preferences(e.g., within a country, international, etc.). The backup agent 502 thenselects (at block 616) the qualifying k-tuple having a “best” score,which may be a lowest or highest score depending on the criteria.

After selecting a qualifying k-tuple at block 612 or block 616, thebackup agent 502 may then designate (at block 618) the target storage ofthe selected k-tuple closest to the source device 500 as a primarytarget storage to which the source data from the source device isbacked-up and designate (at block 620) the other at least one targetstorage of the selected k-tuple not closest to the source device as atleast one secondary target storage to which the source data is backed-upfrom at least one of the other target storages in the selected k-tuple.For instance, once the source data 108 is backed-up to the primarytarget storage 104 ₁, the backed-up source data 108 from the primarytarget storage 104 ₁ may be copied to one of the secondary targetstorages, and each secondary storage 104, to which the source data 108is copied selects another one of the secondary target storages 104_((i+1)) to which the source data 106 is further copied. Each targetstorage 104, may select the closest other target storage 104 _((i+1)) towhich to copy the source data 108 until the source data 106 resides onall the target storages in the selected k-tuple. Alternatively, theprimary target storage 104 ₁ may copy the source data 108 to all thetarget storages 104 ₂ . . . 104 _(k). In a yet further embodiment, thesource device 500 may copy the source data 108 to all the k targetstorages in the selected k-tuple.

If (at block 608) there was no qualifying k-tuple having a set of ktarget storages satisfying the distance (e.g., disaster impact diameter)and/or primary distance limit, then control proceeds to block 622 inFIG. 6b to try to find a (k−1) tuple of (k−1) target storages thatsatisfy the distance and other requirements. At block 622, k isdecremented. If (at block 624) k is not equal to one, then controlproceeds to block 604 in FIG. 6a to try to find a qualifying (k−1) tupleof target storages to provision. If (at block 624) k has beendecremented to one and if (at block 626) there is at least one targetstorage server satisfying a distance requirement (e.g., disaster impactdiameter) and/or a primary distance limitation (PDL) requirement, suchas the same requirements considered at block 604 with respect to thesource device 500, then the backup agent 502 selects (at block 630) theclosest target storage satisfying the requirements (e.g., disasterimpact diameter and/or primary distance limit) with respect to thesource device to provision as the target storage. After selecting onlyone target storage 104 i to use, the backup agent 502 indicates (atblock 632) that only one target storage was available to be configuredfor use with source device 500 given the different distancerequirements. This indication may be provided in a message to anadministrator of the outcome. If (at block 626) there was not one targetstorage satisfying the requirements, then the backup agent 502 indicates(at block 628) (e.g., returns a message) that no target storage 104 ₁,104 ₂ . . . 104 _(m) was available to be configured for use with sourcedevice given distance requirements.

After designating (at blocks 618 and 620) the primary and secondarytarget storages, control proceeds to block 634 in FIG. 6c where thebackup agent 502 initiates a configuration procedure to configure thesource device 500 and the k target storages in the selected qualifyingk-tuple target storage to have the source data 108 in the source device500 backed-up to the primary target storage in the selected qualifyingk-tuple over the network 106 and copy the source data 108 to the atleast one other secondary target storage. In one embodiment, the backupagent 502 may automatically issue APIs and other commands to configurethe source device 500 and the k target storages to backup the sourcedata 108. In an alternative embodiment, the backup agent 502 may provideinformation on the selected k target storages to an administrator orother program to have another entity perform the actual configuration.

If (at block 636) the configuration (or indication of the configuration)completed with all the initial k requested target storages, then thebackup agent 502 indicates (at block 638) that the configurationsuccessfully completed with the k requested target storages, andprovides information on configured target storages, such as distancesfrom each other and the source device. If (at block 636) theconfiguration completed with less than the requested k target storages,then the backup agent 502 indicates (at block 640) that theconfiguration completed with less than the requested k target storagesand information on the configured target storages.

The determination of qualifying k-tuples in FIGS. 6a, 6b, and 6c mayalso be used for other types of network determinations, such as where tolocate a new target storage, source device, or from which location toremove a target storage.

FIG. 7 illustrates an embodiment of operations performed by the backupagent 502 (or 202) or another program to use the operations of FIGS. 6a,6b, and 6c to determine an optimal storage location to use for adding anew target storage to one of a plurality of potential target storagelocations. In other words, the described operations of FIGS. 6a, 6b, and6c may be used for purposes other than provisioning storage to clients,but may also be used to optimize placement of new target storages. Uponinitiating (at block 700) the operations to optimize placement of a newtarget storage, the backup agent 502 performs a loop of operations atblocks 702 through 714 for each potential target storage location ibeing considered, which comprises a geographical location. A loop ofoperations is then performed from blocks 704 through 710 for each of thesource devices j configured in the network 106.

At block 706, the backup agent 502 performs the operations in FIGS. 6a,6b, and 6c to determine a qualifying k-tuple for one or more values of kfor the source device j. The backup agent 502 then determines (at block708) a score based on the selected one or more qualifying k-tuples,which may be based on a distance of the target storages in the one ormore qualifying k-tuples to the source device. The backup agent 502determines (at block 712) a total score for target storage location ibased on the scores determined for all the source devices at block 708when the potential target storage location i was added to the mix oftarget storages, such as by adding the new target storage to the targetstorage data store 504 and source device and target storage table 506.

In this way the optimization considers how a potential storage locationi optimizes selection across each of the source devices 200 ₁, 200 ₂ . .. 200 _(n) in the network 106 by determining a score for each of thepotential storage locations based on the geographical location of thesource devices 200 ₁, 200 ₂ . . . 200 _(n) that will be impacted by theplacement. After determining the total scores for all the potentialtarget storage locations, the backup agent 502 determines (at block 716)the potential target storage location having a total score valueindicating the most optimal storage location. This most optimalpotential target storage location is returned (at block 718) in arecommendation of where to locate the new target storage.

In a further embodiment, if a target storage needs to be removed theoperations of FIG. 7 may be used to determine an optimal possiblelocation from which to remove a target storage by considering thelocation of all the existing target storages 104 ₁, 104 ₂ . . . 104 _(m)as the potential target storage locations for removal. Further, thelogic of FIG. 7 may also be used to determine an optimal location tolocate a source device 200 ₁, 200 ₂ . . . 200 _(n) or to determine theeffect of using different distance and primary distance limitrequirements.

Described embodiments provide techniques to provision target storages toa source device based on the location of the source device and thetarget storage and one or more distance requirements, such as a disasterimpact diameter and/or a primary distance limit for the source device.The described operations are particularly useful in situations where thesource device may be moved or located in different geographicallocations, and the set of qualifying target storages may be changed.With the described embodiments, the selected target storage may beautomatically configured to backup selected source data from the sourcedevice.

Further embodiments provide techniques to select a specified number oftarget storages to provision to provide data protection to a storagedevice considering the geographical locations of the source device andthe target storages with respect to each other. With describedembodiments a group or tuple of target storages having the specifiednumber is selected that satisfy distance and primary distance limitcriteria with respect to the source device. Further, the technique forselecting a best or optimal allocation of specified target servers basedon the geographical locations of the target server and the storagedevice may be used to select an optimal potential target storagelocation at which to provide a new target storage when determining whereto allocate new target storage resources.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The letter designators, such as i, j, k, m, n, used to designate anumber of instances of an element may indicate a variable number ofinstances of that element when used with the same or different elements.

The computational components of FIGS. 1, 2, and 5 including the sourcedevices 200 ₁, 200 ₂ . . . 200 _(n), 200, 500 and target storages 104 ₁,104 ₂ . . . 104 _(m) may be implemented in one or more computer systems,such as the computer system 802 shown in FIG. 8. Computer system/server802 may be described in the general context of computer systemexecutable instructions, such as program modules, being executed by acomputer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.Computer system/server 802 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 8, the computer system/server 802 is shown in the formof a general-purpose computing device. The components of computersystem/server 802 may include, but are not limited to, one or moreprocessors or processing units 804, a system memory 806, and a bus 808that couples various system components including system memory 806 toprocessor 804. Bus 808 represents one or more of any of several types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 802 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 802, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 806 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 810 and/or cachememory 812. Computer system/server 802 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 813 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 808 by one or more datamedia interfaces. As will be further depicted and described below,memory 806 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 814, having a set (at least one) of program modules 816,may be stored in memory 806 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. The components of the computer 802 may be implemented asprogram modules 816 which generally carry out the functions and/ormethodologies of embodiments of the invention as described herein. Thesystems of FIG. 1 may be implemented in one or more computer systems802, where if they are implemented in multiple computer systems 802,then the computer systems may communicate over a network.

Computer system/server 802 may also communicate with one or moreexternal devices 818 such as a keyboard, a pointing device, a display820, etc.; one or more devices that enable a user to interact withcomputer system/server 802; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 802 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 822. Still yet, computer system/server 802can communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 824. As depicted, network adapter 824communicates with the other components of computer system/server 802 viabus 808. It should be understood that although not shown, other hardwareand/or software components may be used in conjunction with computersystem/server 802. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

What is claimed is:
 1. A computer program product for selecting at leastone target storage on which to backup source data from a source devicein a network comprising a plurality of target storages, wherein thecomputer program product comprises at least one computer readablestorage medium including computer program code embodied therewith thatwhen executed performs operations, the operations comprising:determining a geographical location of the source device; determininggeographical locations of target storages; determining a target storagecomprising one of the target storages whose distance from the sourcedevice based on the geographical locations of the source device and thetarget storages satisfies distance requirements comprising a minimumdistance requirement that the target storage must be at least a minimumdistance from the source device to provide a disaster impact diameter toprotect data at the target storage from an area wide disaster and amaximum distance requirement that the target storage be less than amaximum distance from the source device; and initiating a configurationprocedure to configure the source device and the determined targetstorage to have the source data backed-up from the source device to thetarget storage over the network.
 2. The computer program product ofclaim 1, wherein the determining the geographical location of the sourcedevice comprises at least one operation of a set of operationscomprising: issuing a command to obtain the geographical location from alocation device in the source device; using network routing data toestimate the geographical location of the source device; and generatinga user interface requesting a user of the source device to enter thegeographical location of the source device.
 3. The computer programproduct of claim 1, wherein the operations further comprise: maintaininga data store having information on the target storages and theirgeographical locations, wherein determining the geographical locationsof the target storages comprises determining the geographical locationsfrom the data store.
 4. The computer program product of claim 3, whereinthe data store includes storage attributes of the target storages inaddition to the geographical location, wherein the determining thetarget storages comprises: determining the target storages indicated inthe data store having storage attributes satisfying a storage attributepolicy, wherein the determination of the target storages satisfying thedistance requirements comprises determining the target storages havingthe storage attributes satisfying a storage attribute policy whosedistance from the source device satisfies the distance requirements. 5.The computer program product of claim 1, wherein the determined targetstorage whose distance from the source device satisfies one distancerequirements has a distance from the source device greater than theminimum distance requirement and less than the maximum distancerequirement, wherein the minimum distance requirement is less than themaximum distance requirement.
 6. The computer program product of claim5, wherein the disaster impact diameter comprises a distance required toprotect against a disaster impact within the geographical location ofthe source device or target storage and wherein the maximum distancerequirement comprises a primary distance limit indicating a maximumdistance required between at least one of the target storages from thesource device.
 7. The computer program product of claim 6, wherein theprimary distance limit indicates a maximum distance at which the sourcedevice can be located from the target storage and have a data throughputrate that satisfies a minimum data throughput rate threshold fortransferring data between the target storage and the source device. 8.The computer program product of claim 1, wherein the initiating theconfiguration procedure comprises issuing commands to the source deviceand the target storage to configure the source device and the targetstorage to backup the source data to the target storage over thenetwork.
 9. The computer program product of claim 1, wherein theinitiating the configuration procedure comprises notifying anadministrator of an assignment of the determined target storage tobackup the source data to enable the administrator to configure thesource device and the determined target storage to backup the sourcedata over the network.
 10. The computer program product of claim 1,wherein the computer program product is implemented in a managementserver in communication with the source device and the target storagesover the network, wherein the management server configures the sourcedevice and the determined target storage to have the source databacked-up from the source device to the target storage over the network.11. A system for selecting at least one target storage on which tobackup source data from a source device in a network comprising aplurality of target storages, comprising: a processor; and a computerreadable storage medium having program instruction that when executedperform operations, the operations comprising: determining ageographical location of the source device; determining geographicallocations of target storages; determining a target storage comprisingone of the target storages whose distance from the source device basedon the geographical locations of the source device and the targetstorages satisfies distance requirements comprising a minimum distancerequirement that the target storage be at least a minimum distance fromthe source device to provide a disaster impact diameter to protect dataat the target storage from an area wide disaster and a maximum distancerequirement that the target storage be less than a maximum distance fromthe source device; and initiating a configuration procedure to configurethe source device and the determined target storage to have the sourcedata backed-up from the source device to the target storage over thenetwork.
 12. The system of claim 11, wherein the determined targetstorage whose distance from the source device satisfies the distancerequirements has a distance from the source device greater than theminimum distance requirement and less than the maximum distancerequirement, wherein the minimum distance requirement is less than themaximum distance requirement.
 13. The system of claim 12, wherein thedisaster impact diameter comprises a distance required to protectagainst a disaster impact within the geographical location of the sourcedevice or target storage and wherein the maximum distance requirementcomprises a primary distance limit indicating a maximum distancerequired between at least one of the target storages from the sourcedevice.
 14. The system of claim 13, wherein the primary distance limitindicates a maximum distance at which the source device can be locatedfrom the target storage and have a data throughput rate that satisfies aminimum data throughput rate threshold for transferring data between thetarget storage and the source device.
 15. The system of claim 11,wherein the determining the geographical location of the source devicecomprises at least one operation of a set of operations comprising:issuing a command to obtain the geographical location from a locationdevice in the source device; using network routing data to estimate thegeographical location of the source device; and generating a userinterface requesting a user of the source device to enter thegeographical location of the source device.
 16. The system of claim 11,wherein the operations further comprise: maintaining a data store havinginformation on the target storages and their geographical locations,wherein determining the geographical locations of the target storagescomprises determining the geographical locations from the data store.17. The system of claim 16, wherein the data store includes storageattributes of the target storages in addition to the geographicallocation, wherein the determining the target storages comprises:determining the target storages indicated in the data store havingstorage attributes satisfying a storage attribute policy, wherein thedetermination of the target storages satisfying the distancerequirements comprises determining the target storages having thestorage attributes satisfying a storage attribute policy whose distancefrom the source device satisfies the distance requirements.
 18. Thesystem of claim 11, wherein the initiating the configuration procedurecomprises issuing commands to the source device and the target storageto configure the source device and the target storage to backup thesource data to the target storage over the network.
 19. The system ofclaim 11, wherein the initiating the configuration procedure comprisesnotifying an administrator of an assignment of the determined targetstorage to backup the source data to enable the administrator toconfigure the source device and the determined target storage to backupthe source data over the network.
 20. The system of claim 11, whereinthe system comprises a management server in communication with thesource device and the target storages over the network, wherein themanagement server configures the source device and the determined targetstorage to have the source data backed-up from the source device to thetarget storage over the network.